ServerPause

Syntax: @ServerPause attribute[, attribute]

The ServerPause command enables attributes to be specified as being "OLE2 supplied". When an OLE2 supplied attribute requires a value, XpertRule will enter a loop in order to give an OLE2 client application an opportunity to supply the value.

An attribute can be designated as "OLE2 supplied" by placing the @ServerPause command, with no parameters, in a procedure tied to the attribute. Outcomes can also be designated as OLE2 supplied (in this case being passed to the client) by placing the @ServerPause command in a procedure tied to the outcome. Alternatively, the @ServerPause command can be placed in any suitable procedure and be followed by one or several attribute names.

The @ServerPause command is specifically for use with OLE2.

Examples

@ServerPause

This command in a procedure would designate any attribute that the procedure is tied to as being OLE2 supplied.

@ServerPause Grade, Cost, Department

This command would set the following three attributes to be designated as OLE2 supplied. Note that when ServerPause is used with such a list of attributes, that any attribute that the procedure is tied to would not automatically also be set to OLE2 supplied. It must be included in the list if this is required.

Note that ServerPause will only take effect when XpertRule is called as a server application. If you run XpertRule directly (i.e. NOT from within the client application) the ServerPause commands are simply ignored and normal attribute prompt dialogs will be used. This enables the testing of your application in isolation from the OLE links.